misc scripts: add support for arm64#12639
Conversation
michelroegl-brunner
left a comment
There was a problem hiding this comment.
Looks like a solid solution to implement the ARM scripts in the repo. We then dont even need any special calls for the scripts when a user wants to run the arm version. I really like that. As i see for the install script, you just basicly put the arm needed stuff in front of the AMD64 install script?
CrazyWolf13
left a comment
There was a problem hiding this comment.
Was this tested in VED repo?
Should we consider adding a short whitail popup, that arm support is in beta or active development and there may be stuff that is not yet fully tested/working?
Co-authored-by: Tobias <96661824+CrazyWolf13@users.noreply.github.com>
Co-authored-by: Tobias <96661824+CrazyWolf13@users.noreply.github.com>
Co-authored-by: Tobias <96661824+CrazyWolf13@users.noreply.github.com>
Co-authored-by: Tobias <96661824+CrazyWolf13@users.noreply.github.com>
Legacy support removed since no cts use them anymore.
Add clearer architecture error messages and gate arm64 usage, plus implement architecture-aware behavior across the toolkit. Changes include: update exit-code messages to reference amd64/arm64, refuse arm64 unless explicitly enabled, show architecture in summaries, and use arch-specific package lists when installing in containers. Make downloads for FFmpeg and yq choose the correct amd64/arm64 binaries, tighten template download error handling and formatting, and clean up minor whitespace/comment issues. These changes aim to make arm64 handling explicit and downloads/installations more robust for non-amd64 systems.
|
I don't see any outstanding issues here. If @MickLesk agrees, we can merge this |
CrazyWolf13
left a comment
There was a problem hiding this comment.
I don't see any issues with it, but @MickLesk is the most familiar with core
There was a problem hiding this comment.
Pull request overview
This PR extends the helper scripts’ architecture handling to (intendedly) support arm64 hosts/containers, including arm64-aware template fetching for Debian/Ubuntu/Alpine and arm64 binary selection for a few bundled tools.
Changes:
- Update GitHub/Codeberg release asset selection heuristics to better distinguish amd64 vs arm64
.debassets. - Add arm64-specific LXC template download flow (GitHub releases + linuxcontainers Jenkins rootfs) and wire it into container creation.
- Add arm64-aware download URLs for selected tools (FFmpeg/yq) and adjust architecture validation messaging.
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 10 comments.
Show a summary per file
| File | Description |
|---|---|
misc/tools.func |
Refines release asset heuristics and adds arch-based FFmpeg/yq download selection. |
misc/error_handler.func |
Updates exit-code 106 description text to reflect amd64/arm64 support. |
misc/core.func |
Expands arch validation to include arm64, adds whiptail install helper + arm64 notice dialog. |
misc/build.func |
Adds ARM64 template defaults and implements custom arm64 template download/validation in LXC creation. |
misc/api.func |
Updates exit-code 106 description text to reflect amd64/arm64 support. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
We should prepare the Website (issue Template and Request form for arm64) the issue Template and some little Things. Maybe i have in the next week an arm64 Test Setup |
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
16ac440
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
5ec219a to
88a6b07
Compare
|
@MickLesk what do you want changed on the website for that to get merged? i can tackle some things if you like. |
|
Sure, you can. My brain is full this week 😄 and its fckn monday |
|
@MickLesk review/approve when you got time pls |
✍️ Description
Adds support for creating arm64 Ubuntu, Debian, and alpine containers via scripts.
✅ Prerequisites (X in brackets)
🛠️ Type of Change (X in brackets)
README,AppName.md,CONTRIBUTING.md, or other docs.